Information processing system for billing system and billing information collection method

ABSTRACT

When a call connection request is transmitted from MS  1  a link is established by PPP processing part  242  and billing control system  245  makes communication timer  244  start counting communication time. If communication conditions over the wireless section deteriorate and/or if there is no transmission/reception of data frames, billing control system  245  makes communication timer  244  halt counting of communication time. Further, if transmission/reception of data resumes, a connection over the wireless section is re-established by BSC  23  and billing control system  245  makes communication timer  244  recover counting of communication time. Finally, if data communication with server  4  is closed, billing control system  245  makes communication timer  244  stop counting communication time.

BACKGROUND OF THE INVENTION

[0001] 1. Field of the Invention

[0002] The present invention concerns technology for collecting billinginformation, and more specifically, technology that enables appropriatetime counting of communication time of billing information for aterminal even where the connection over a wireless section is releasedwhile data communication is taking place.

[0003] 2. Description of Related Art

[0004] One recent format for network connectivity over the Internetinvolves connecting mobile telephones for example to something likemobile terminals providing connectivity via wireless channels. Onemethod for data communication performed via wireless channels is thedigital cellular system CDMA (Code Division Multiple Access). Among theIS-95 A and B (IS-95A/B) standards and the EIA/TIA-707A standards ofthis CDMA methodology there are standards for procedures for connectingan MS (Mobile Station) to a connectionless network using IP (InternetProtocol) and there is a method of performing data communication via IWF(Inter working Function).

[0005] For the configuration of a billing information collection systemfor billing something like mobile terminals that perform datacommunication, guidelines are described in the CDMA Mobile IPImplementation Guideline Version 1.5 published by the CDG (CDMADevelopment Group) and the materials of the TIA/EIA, TR45. 6/99. 05.17-06 Wireless IP Network Architecture Based on IETF, while WO97/26739shows a configuration that includes billing nodes and a billing system.

[0006] For example, a system for collecting billing information, asshown in FIG. 11, comprises MS (mobile station) 1 and switching system 2as well as billing system 3 that collects billing information collectedat this switching system 2. This switching system 2 comprises BTS (BaseTransceiver System) 21, MSC (Mobile Switching Center) 22, BSC (BaseStation Controller) 23 and IWF (Inter working Function) 24.

[0007] As shown in FIG. 11, the protocol stack of MS 1 and IWF 24 hasIS-95A/B, RLP (Radio Link Protocol), PPP (Point to Point Protocol),TCP/IP (Transport Control Protocol/Internet Protocol) and APL(Application).

[0008] Operations of the above configuration will now be described.

[0009] When BSC 23 receives a call connection request from MS 1, BSC 23establishes an IS-95 A/B connection at a subordinate layer and allocateschannels to be used.

[0010] IWF 24 terminates a PPP connection to establish a PPP connectionfor MS 1.

[0011] Once IWF 24 establishes a PPP connection, extraction of billinginformation commences.

[0012] This billing information includes the communication time, totalnumber of packets transmitted, total number of packets received, thetotal size of packets transmitted cumulatively and the total size ofpackets received cumulatively.

[0013] Next, MS 1, BSC 23 and IWF 24 monitor flow volume of data frameson transmission channels or volume of data frames in their own buffers,while if for a specified time data frames in transmission channels ortheir own buffers cannot be detected, MS 1, BSC 5 and IWF 6 release theIS-95 A/B connection over the wireless section. Because a PPP connectionbetween MS 1 and IWF 6 is established when there is a call connectionrequest, even if the IS-95 A/B connection is released the PPP connectioncontinues. Further, release of the IS-95 A/B connection on a subordinatelayer in the wireless section is also prescribed in IS-707.

[0014] If MS 1, BSC 23 and IWF 24 detect data frames on the transmissionchannels or their own buffer, they re-establish the IS-95 A/Bconnection.

[0015] When data communication with MS 1 is closed, billing informationis transferred to billing system 3. Communication time, that is one partof billing information, is the total communication time from theestablishment of the PPP connection of IWF 24 until the connection isdisconnected or it may be the time used by resources of switching system2.

[0016] Nonetheless, with the configuration described above, a problemexists because a PPP connection remains established even if the IS-95A/B connection over the wireless section is released and thiscommunication time is counted for the billing information so appropriatebilling information cannot be obtained.

[0017] Further, a problem arises to remove time in which the IS-95 A/Bconnection is released, because when an IS-95 A/B connection is releasedor when an IS-95 A/B connection is re-established, if the information onthe IS-95 A/B connection being released or re-established is, in thecircumstances, transmitted from the switching system to the billingsystem, the volume of traffic increases significantly resulting indeteriorating transmission efficiency.

SUMMARY OF THE INVENTION

[0018] Against the background of the above-mentioned problems, theobject of the present invention is to provide technology that enablesappropriate timing control over communication time in billinginformation even when the connection over a wireless section has beenreleased.

[0019] The above-mentioned problems are solved by an informationprocessing system for a billing system wherein billing information on aterminal connected via wireless channels is collected and this collectedbilling information is transmitted to and stored in a billing server,which comprises a communication time counting means that starts and/orstops counting of communication time to the terminal in response to acall connection request or call disconnection request transmitted fromthe terminal, a detection means for detecting data transmitted to theterminal and/or from the terminal, a control means that halts countingof communication time by the communication time counting means if thedetection means detects data or recovers counting of communication timeby the communication time counting means if the detection means does notdetect data, and a transmission means that transmits billing informationincluding communication time counted by the communication time countingmeans.

[0020] The information processing system further comprises a timecounting means for counting time during the period in which data is notdetected by the detection means and the control means is configured soas to terminate counting of communication time by the communication timecounting means if time counted by the time counting means exceeds aspecified amount.

[0021] The control means may be configured such that a datacommunication close request instructing that communication of data tothe terminal be closed can be transmitted if time counted by thecounting means exceeds a specified amount.

[0022] The above-mentioned problems are solved through a billinginformation collection method that is a method for collection of billinginformation for data communication, that utilizes a billing system thathas an information processing system, a terminal and a billing server,which method comprises a step to start counting communication time basedon a call connection request transmitted from the terminal to theinformation processing system, a detection step for detecting datatransmission to the terminal and data transmission from the terminal, astep for halting counting the time of data transmission if datatransmission to the terminal and/or data transmission from the terminalare not detected, a step to recover the counting of time of datatransmission if data transmission to the terminal or data transmissionfrom the terminal is detected, a step for stopping counting datatransmission time based on a call disconnection request transmitted fromthe terminal and a step to transmit billing information includingtransmission time thus counted to the billing server.

[0023] The billing information collection method further comprises astep for counting the time during which the information processingsystem does not detect data transmission to the terminal or datatransmission from the terminal and a step for stopping counting oftransmission time and transmitting to the terminal a data communicationdose request instructing that communication of data to the terminal beclosed, if time counted exceeds a specified amount.

BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Specific embodiments of the present invention will now bedescribed, by way of example only, with reference to the accompanying ofdrawings in which:

[0025]FIG. 1 is a block diagram showing a system for collecting billinginformation according to a first embodiment of this invention;

[0026]FIG. 2 is a block diagram of IWF according to a first embodimentof this invention;

[0027]FIG. 3 is a flowchart showing operations according to a firstembodiment of this invention;

[0028]FIG. 4 shows the transition of internal conditions in the PPPprocessing part;

[0029]FIG. 5 shows the protocol stack;

[0030]FIG. 6 shows the protocol stack;

[0031]FIG. 7 shows the protocol stack;

[0032]FIG. 8 shows communication time of billing information;

[0033]FIG. 9 is a block diagram of IWF according to a second embodimentof this invention;

[0034]FIG. 10 is a flowchart showing operations according to a secondembodiment of this invention; and

[0035]FIG. 11 is a block diagram showing an existing system forcollecting billing information.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0036] A first embodiment of this invention will now be described.

[0037] In the first embodiment of this invention, if there is atemporary discontinuance of data transmission and/or reception betweenan MS and information server while data communication between the MS andinformation server is taking place, the time during which that datatransmission and/or reception discontinuance occurs is not includedwithin communication time that comprises one of the items of billinginformation for the MS.

[0038] The first embodiment will now be described in detail.

[0039]FIG. 1 is a block diagram showing a system for collecting billinginformation according to the first embodiment of this invention. FIG. 2is a block diagram of IWF. FIG. 3 is a flowchart showing operationsaccording to a first embodiment of this invention. FIG. 4 shows thetransition between conditions in the PPP processing part. FIGS. 5through 7 show the protocol stack and FIG. 8 shows communication timefor billing information.

[0040] As shown in FIG. 1, the billing information collection system iscomprised of MS (Mobile Station) 1, switching system 2, billing system3, server 4 and IP network 5 that provides mutual connectivity betweenswitching system 2 and billing system 3.

[0041] This switching system 2 comprises BTS (Base Transceiver System)21, MSC (Mobile Switching Center, not shown in FIG. 1), BSC (BaseStation Controller) 23 and IWF (Inter working Function) 24 according tothis invention.

[0042] MS 1, which may be a personal computer or a mobile telephone forexample, performs data communication with remote server 4 via thenetwork. To perform data communication with this remote server 4, MS 1connects to switching system 2 via wireless channels (wireless section),and transmits data frames of wireless protocol format to switchingsystem 2.

[0043] Something like the Internet or an internal company LAN areconceivable as examples of the network at this point.

[0044] MS 1 transmits a connection request to switching system 2 forconnecting to switching system 2 and a disconnect request fordisconnecting from switching system 2.

[0045] If communication conditions over the wireless sectiondeteriorate, or if for a specified period of time there is notransmission of data frames of wireless protocol format to switchingsystem 2 moreover, and data frames of wireless protocol format are notreceived transmitted from switching system 2, MS 1 transmits toswitching system 2 a connection release request for the connection overthe wireless section. If however communication conditions over thewireless section recover or transmission of data frames of wirelessprotocol format to switching system 2 occurs, MS 1 transmits areconnection request for the connection over the wireless section toswitching system 2

[0046] If BTS 21 receives data frames of wireless protocol format fromMS 1, BTS 21 transmits those data frames to BSC 23, and if BTS 21receives data frames of wireless protocol format from BSC 23, BTS 21transmits those data frames to MS 1.

[0047] If BSC 23 receives a call connection request from MS 1 via BTS21, BSC 23 establishes a connection over the wireless section andallocates channels to be used for the connection, BSC 23 transmits toIWF 24 data frames of wireless protocol format transmitted from BTS 21and transmits to BTS 21 data frames of wireless protocol formattransmitted from IWF 24.

[0048] If BSC 23 receives a call disconnection request from MS 1, inaddition to disconnecting the connection over the wireless section, BSC23 transmits a PPP disconnection request to IWF 23, while if BSC 23receives a disconnection request for the connection over the wirelesssection from IWF 24, BSC 23 transmits a call disconnection request to MS1 via BTS 21, disconnects the connection over the wireless section andcloses data communication with MS 1.

[0049] BSC 23 monitors communication conditions over the wirelesssection and if it detects a deterioration in those conditions, BSC 23transmits a connection release request for the connection over thewireless section to MS 1 via BTS 21. If however, BSC 23 detects arecovery in communication conditions over the wireless section, BSC 23transmits to MS 1 via BTS 21 a connection re-establishment request forthe connection over the wireless section for re-establishing theconnection over the wireless section. IWF 24 also detects the release orre-establishment of such connections over the wireless section andimplements control over counting of communication time.

[0050] IWF 24 converts data frames of wireless protocol format into IPpacket format and also acts as a protocol conversion means performingconversions in the opposite direction, making a decision whether or notdata frames of wireless protocol format are being transmitted from BSC23, so that if, temporarily, such data frames are not being transmittedfrom BSC 23, IWF 24 transmits a connection release request for theconnection over the wireless section to BSC 23, facilitating the releaseof the connection over the wireless section. The occurrence of dataframes of wireless protocol format moving from MS 1 to the IP network atthis point is equivalent to a request for a reconnection over thewireless section issued from MS 1, and is therefore detected by IWF 24.On the other hand, when IWF 24 detects the occurrence of data thatshould be transmitted to MS 1, that is to say, IWF 24 detects datamoving from the IP network to MS 1, IWF 24 transmits to BSC 23 aconnection re-establishment request for the connection over the wirelesssection, for re-establishing the connection over the wireless section.

[0051] As shown in FIG. 2, IWF 24 comprises wireless interface part 241,PPP processing part 242, TCP/IP processing part 243, communication timer244, billing control part 245 and link control part 246.

[0052] Wireless interface part 241 stores wireless protocol format dataframes from BSC 23 in buffer 241A and once a specified volume of suchdata frames is reached, those data frames are transmitted to PPPprocessing part 242 and link control part 246.

[0053] Wireless interface part 241 stores wireless protocol format dataframes from PPP processing part 242 in buffer 241B and once a specifiedvolume of such data frames is reached, those data frames are transmittedto BSC 23. Although not shown in the drawings, wireless interface part241 transmits connection release request and reconnection requestsignals for a connection over a wireless section, which signals arecontrolled by link control part 246, to BSC 23.

[0054] PPP processing part 242 deciphers wireless protocol data framesfrom wireless interface part 241, converting the IP packets andtransmits these IP packets to TCP/IP processing part 243.

[0055] Further, if PPP processing part 242 receives IP packets fromTCP/IP processing part 243, part 242 converts these IP packets intowireless protocol format data frames and transmits them to wirelessinterface part 241. The method for converting from wireless protocolformat data frames to IP packets, the method for converting from IPpackets to wireless protocol format data frames and the procedures forPPP protocol connection are known, existing technology. Accordingly, nodetailed explanation of these procedures and methods is offered here.

[0056] Moreover, PPP processing part 242 establishes a PPP protocolconnection based on data input from wireless interface part 241 and oncethe connection is established, part 242 transmits to billing controlpart 245 a time count start signal instructing that counting ofcommunication time commences. Once part 242 receives a PPP connectiondisconnection request from link control part 246 (describedsubsequently), part 242 makes the link dead and in addition todisconnecting the connection of PPP protocol, transmits to billingcontrol part 245 a time count stop signal instructing that counting ofcommunication time stops.

[0057] Moreover, if PPP processing part 242 receives a link halt signalfrom link control part 246, in addition to halting the PPP protocollink, part 242 transmits to billing control part 245 a time count haltsignal to halt time counting of communication time. Once part 242receives a recover link signal from part 246, in addition to recoveringthe PPP protocol link, part 242 transmits to part 245 a time countrecovery signal to recover counting of communication time.

[0058] TCP/IP processing part 243 stores IP packets from PPP processingpart 242 in buffer 243A and once a specified volume of such IP packetsis reached, part 243 transmits those packets to IP network 5. Part 243stores IP packets from IP network 5 in buffer 243B and once a specifiedvolume of such IP packets is reached, part 243 transmits those packetsto part 242 and link control part 246.

[0059] TCP/IP processing part 243 transmits billing information frombilling control part 245 to billing system 3.

[0060] Communication timer 244 measures communication time with MS 1 inaccordance with instructions from billing control part 245.

[0061] In addition to stopping counting of communication time bycommunication timer 244, billing control part 245 is a part thatmeasures the total number of packets transmitted, total number ofpackets received, the total size of packets transmitted cumulatively andthe total size of packets received cumulatively.

[0062] When billing control part 245 receives a time count start signalfrom PPP processing part 242, part 245 makes communication timer 244start counting time. When part 245 receives a time count halt signalfrom part 242, part 245 makes timer 244 temporarily halt time countingand when part 245 receives a time count recovery signal from part 242,part 245 makes timer 244 recover time counting.

[0063] When billing control part 245 receives a time count stop signalfrom PPP processing part 242, in addition to making communication timer244 stop counting communication time, part 245 reads-out communicationtime counted by timer 244 and transmits billing information includingthe communication time thus read-out to TCP/IP processing part 243.

[0064] Link control part 246 monitors wireless protocol format dataframes stored in buffer 241A of wireless interface part 241 and IPpackets stored in buffer 243B of TCP/IP processing part 243. If suchwireless protocol format data frames stored in buffer 241A of part 241and/or such IP packets stored in buffer 243B of part 243 are no longerpresent, part 246 transmits a link halt signal to PPP processing part242.

[0065] When wireless protocol format data frames are re-stored in buffer241A of wireless interface part 241 or when IP packets are re-stored inbuffer 243B of TCP/IP processing part 243, link control part 246transmits a recover link signal to PPP processing part 242.

[0066] Billing system 3 is the same as existing billing systems andstores billing information received transmitted from switching system 2.

[0067] Server 4 performs data transmission with MS 1.

[0068] Operations occurring in the above configuration will now bedescribed.

[0069] The following operations as described are operations for theperformance of call disconnect, lead by MS 1. The information processingsystem for a billing system of this invention and the billinginformation processing methods as they pertain to performance of adisconnect from the switching system 2 side (not shown in the drawings),are not the subject of inquiry here and are therefore omitted from thedescription.

[0070] To perform data transmission with server 4 MS 1 transmits to BSC23 via BTS 21 a call connection request for a connection over a wirelesssection. Upon receiving this call connection request, BSC 23 establishesa connection over the wireless section (Step 101).

[0071] Once a connection is established over the wireless section, MS 1transmits wireless protocol format data frames. Upon receiving such dataframes, BSC 23 transmits these data frames to IWF 24 and requestsconversion to PPP (Step 102).

[0072] Wireless interface part 241 of IWF 24 stores wireless protocolformat data frames from BSC 23 in buffer 241A and transmits the dataframes thus stored in buffer 241A to PPP processing part 242. Uponreceiving these data frames part 242 deciphers them, establishes a PPPconnection (Step 103), and as shown in FIG. 4, establishes a link.

[0073] PPP processing part 242 performs authentication based on dataincluded in wireless protocol format data frames and makes its conditiontransition to the network layer condition.

[0074] Further, once PPP processing part 242 has completed establishingthe link, in addition to converting wireless protocol format data framesinto IP packets, part 242 transmits to billing control part 245 a timecount start signal instructing that counting of communication timecommences. Upon receiving this time count start signal, part 245, inaddition to making communication timer 244 start counting communicationtime, commences counting the number of packets transmitted or receivedand the number of bytes transmitted or received (Step 104).

[0075] TCP/IP processing part 243 stores IP packets from PPP processingpart 242 in buffer 243A and transmits such IP packets stored in buffer243A to IP network 5.

[0076] In this way, transmission and reception of IP packets performedbetween MS 1 and IP network 5 occurs via wireless interface part 241 ofIWF 24, PPP protocol control part 242 and TCP/IP processing part 243.Further, as shown in FIG. 5, when data communication is performedbetween MS 1 and server 4, the condition of the protocol stack is thatconnections of all layers (IS95A/B, RLP, PPP, TCP/IP. APL) aremaintained.

[0077] If communication conditions over the wireless section deteriorateand/or if there is no transmission/reception of data frames, MS 1transmits a connection release request for the connection over thewireless section. Upon receiving this release request BSC 23 releasesthe connection over the wireless section (Step 105). As shown in FIG. 6,the condition of the protocol stack in this situation is that theconnection over the wireless section (IS95A/B, RLP) is released and aconnection on a higher layer than the wireless section (PPP, TCP/IP.APL) is in an established state.

[0078] Link control part 246 detects that wireless protocol format dataframes transmitted from wireless interface part 241 have not beenreceived and transmits a link halt signal to PPP processing part 242. Asshown in FIG. 4, upon receiving this link halt signal, part 242 makesits internal condition transition from the network layer condition tothe link halt condition and transmits a time count halt signal tobilling control part 245 (Step 106). At this time, part 246 monitors IPpackets stored in buffer 243B of TCP/IP processing part 243 and confirmsthat there are no IP packets present. If, at this point, IP packets werepresent, part 246 would, in addition to transmitting a recover linksignal to part 242, initiate a reconnection over the wireless section byBSC 23.

[0079] If billing control part 245 receives a time count halt signalfrom PPP processing part 242, part 245 makes communication timer 244halt time counting (Step 107) so that, while counting itself of thenumber of transmitted/received packets and the number oftransmitted/received bytes by part 245 is not stopped, datacommunication is halted so those packets and bytes are not counted.

[0080] Thereafter, if data for transmission arises, MS 1 transmits areconnection request for the connection over the wireless section to BSC23. Upon receiving this reconnection request, BSC 23 establishes aconnection over the wireless section (Step 108).

[0081] Once a connection over the wireless section is established, MS 1transmits wireless protocol format data frames. Upon receiving such dataframes, BSC 23 transmits wireless protocol format data frames to IWF 24.

[0082] Link control part 246 detects wireless protocol format dataframes stored in buffer 241A of wireless interface part 241, so part 246transmits a recover link signal to PPP processing part 242. Uponreceiving this recover link signal, part 242 makes its internalcondition transition from the link halt condition to the network layercondition as shown in FIG. 4. The condition of the protocol stack atthis time, is, in the same manner as when data communication isperformed between MS 1 and server 4, that connections of all layers(IS95A/B, RLP, PPP, TCP/IP. APL) are in an established state, as shownin FIG. 7.

[0083] Moreover, PPP processing part 242 makes its internal conditiontransition to the network layer condition and transmits a time countrecovery signal to billing control part 245 (Step 109). Upon receivingthis signal, part 245 makes communication timer 244 recover timecounting of communication time (Step 110).

[0084] Next, when MS 1 is going to closes data communication with server4, MS 1 transmits to BSC 23 via BTS 21, a call disconnection requestrequesting release of the connection over the wireless section andclosure of data transmission (Step 111).

[0085] Upon receiving a call disconnection request from MS 1, BSC 23releases the connection over the wireless section and transmits a PPPconnection disconnection request to IWF 24. Upon receiving this PPPconnection disconnection request, PPP processing part 242 of IWF 24makes its internal condition transition from the network layer conditionto the link disconnected condition, as shown in FIG. 4, and furthermakes its internal condition transition from the link disconnectedcondition to the link dead condition (Step 112).

[0086] PPP processing part 242 transmits a time count stop signal tobilling control part 245. Upon receiving this signal, part 245 makescommunication timer 244 stop counting communication time. As shown inFIG. 8, for example, total communication time from reception of a callconnection request until reception of a call disconnection request (fromgeneration of the call connection until disconnection of the callconnection) is Tm time. If data communication is interrupted becausecommunication conditions over the wireless section deteriorate or thereis no transmission/reception of data frames, the length of interruptionof communication time for the period of interruption of datacommunication would be Ti1 time and Ti2 time, so communication time ascounted by timer 244 would be Tm-Ti1-Ti2 (Step 113).

[0087] Billing control part 245 reads-out communication time counted bycommunication timer 244 and transmits billing information including thecommunication time thus read-out to TCP/IP processing part 243 (Step114). Upon receiving this billing information part 243 transmits tobilling system 3 this billing information and information indicatingclosure of data communication showing that data communication with MS 1has closed (Step 115).

[0088] Upon receiving information indicating closure of datacommunication and billing information from TCP/IP processing part 243,billing system 3 stores this billing information (Step 116).

[0089] A second embodiment of this invention will now be described.

[0090] In the second embodiment of this invention the length of timethat a connection over a wireless section is released is counted and ifthat time exceeds a specified amount of time, in addition to datacommunication being closed, time counting of communication time isstopped.

[0091] The second embodiment will now be described in detail.

[0092]FIG. 9 is a block diagram of IWF. FIG. 10 is a flowchart showingoperations according to a second embodiment of the present invention.

[0093] Things which are of the same configuration as for the firstembodiment are marked with the same numbers and a detailed explanationof them is omitted.

[0094] In accordance with instructions from link control part 248, linktimer 247 performs time measurement of the time in which the internalconditions of PPP processing part 242 are in the link halt condition.

[0095] Link control part 248 monitors buffer 241A of wireless interfacepart 241 and buffer 243B of TCP/IP processing part 243 and when wirelessprotocol format data frames are not stored in buffer 241A moreover IPpackets are not stored in buffer 243B, in addition to transmitting alink halt signal to PPP processing part 242, part 248 makes link timer247 start time counting.

[0096] Further, if wireless protocol format data frames are not storedin buffer 241A and/or IP packets are not stored in buffer 243B, inaddition to transmitting a recover link signal to PPP processing part242, link control part 248 makes link timer 247 stop time counting andresets link timer 247.

[0097] Moreover, if time counted by link timer 247 exceeds a specifiedamount link control part 248 transmits a PPP connection disconnectionrequest to PPP processing part 242.

[0098] Operations of the above configuration will now be described.

[0099] To perform data transmission with server 4, MS 1 transmits to BSC23 via BTS 21 a call connection request for a connection over a wirelesssection. Upon receiving this call connection request, BSC 23 establishesa connection over the wireless section (Step 201) and, in addition totransmitting wireless protocol format data frames from MS 1 to IWF 24,BSC 23 transmits to IWF 24 a conversion request requesting conversion ofthese data frames thus transmitted to PPP (Step 202).

[0100] PPP processing part 242 of IWF 24 deciphers the wireless protocolformat data frames from BSC 23, establishes a PPP connection andestablishes a link (Step 203).

[0101] Further, in addition to converting wireless protocol format dataframes into IP packets, PPP processing part 242 of IWF 24 transmits tobilling control part 245 a time count start signal instructing thatcounting of communication time commences. Upon receiving this time countstart signal, part 245, in addition to making communication timer 244start counting communication, starts counting the number of packetstransmitted or received and the number of bytes transmitted or received(Step 204).

[0102] TCP/IP processing part 243 transmits IP packets from PPPprocessing part 242 to network 5.

[0103] Next, link control part 248 monitors buffer 241A of wirelessinterface part 241 and buffer 243B of TCP/IP processing part 243 (Step205).

[0104] When wireless protocol format data frames are not stored inbuffer 241A moreover IP packets are not stored in buffer 243B, linkcontrol part 248, in addition to transmitting a link halt signal to PPPprocessing part 242, makes link timer 247 start time counting (Step206).

[0105] Further, part 248 monitors buffer 241A to ascertain whether ornot wireless protocol format data frames are stored there and monitorsbuffer 243B to ascertain whether or not IP packets are stored there(Step 207).

[0106] If wireless protocol format data frames are not stored in buffer241A and/or IP packets are not stored in buffer 243B, in addition totransmitting a recover link signal to PPP processing part 242, linkcontrol part 248 makes link timer 247 stop time counting and resets linktimer 247 (Step 208).

[0107] If time counted by link timer 247 exceeds a specified amount linkcontrol part 248 transmits a PPP connection disconnection request to PPPprocessing part 242 (Step 209). Upon receiving this link disconnectionrequest, part 242 makes its internal condition transition from thenetwork layer condition to the link closed condition and further makesits internal condition transition from the link closed condition to thelink dead condition.

[0108] Link control part 248 then transmits to BSC 23 via wirelessinterface part 241 a close request for the connection over the wirelesssection instructing that data communication with MS 1 be closed. Uponreceiving this connection disconnection request, BSC 23 transmits a calldisconnection request to MS 1 and makes data communication with MS 1stop (Step 210).

[0109] PPP processing part 242 transmits a time count stop signal tobilling control part 245. Upon receiving this signal, part 245 makescommunication timer 244 stop counting communication time (Step 211),reads-out communication time counted by timer 244 and transmits billinginformation including the communication time thus read-out to TCP/IPprocessing part 243 (Step 212).

[0110] If TCP/IP processing part 243 receives billing information frombilling control part 245, part 243 transmits to billing system 3 thisbilling information and information indicating closure of datacommunication showing that data communication with MS 1 has closed (Step213). Billing system 3 receives this information indicating closure ofdata communication and billing information and stores it (Step 214).

[0111] A significant effect achieved according to this invention is thateven when, due to a deterioration in communication conditions forexample over a wireless section, the connection over the wirelesssection is released, because communication time during the time periodin which the connection over the wireless section was released is notincluded in billing information, appropriate billing information can becollected.

[0112] A further significant effect achieved according to this inventionis that there is no increase in the volume of traffic of a billingsystem because when the connection over a wireless section is releasedor reconnected, there is no need for any notification signal from aswitching system to the billing system.

[0113] Another significant effect achieved according to this inventionis that there is no need for a change of billing system and an existingbilling system can therefore be used.

What is claimed is:
 1. An information processing system for a billingsystem wherein billing information on a terminal connected via wirelesschannels is collected and said collected billing information istransmitted to and stored in a billing server, which comprises: acommunication time counting means that starts and/or stops counting ofcommunication time to said terminal in response to a call connectionrequest or call disconnection request transmitted from said terminal; adetection means for detecting data transmitted to said terminal and/orfrom said terminal; a control means that halts counting of communicationtime by said communication time counting means if said detection meansdetects data or recovers counting of communication time by saidcommunication time counting means if said detection means does notdetect data; and a transmission means that transmits billing informationincluding communication time counted by said communication time countingmeans.
 2. The information processing system according to claim 1 whichfurther comprises a time counting means for counting time during theperiod in which data is not detected by said detection means and saidcontrol means is configured so as to terminate counting of communicationtime by said communication time counting means if time counted by saidtime counting means exceeds a specified amount.
 3. The informationprocessing system according to either claim 1 or claim 2 wherein saidcontrol means is configured such that a data communication close requestinstructing that communication of data to said terminal be closed can betransmitted if time counted by said counting means exceeds a specifiedamount.
 4. A billing information collection method that is a method forcollection of billing information for data communication, that utilizesa billing system that has information processing equipment, a terminaland a billing server, which comprises: a step to start countingcommunication time based on a call connection request transmitted fromsaid terminal to said information processing equipment; a detection stepfor detecting data transmission to said terminal and data transmissionfrom said terminal; a step for halting counting the time of datatransmission if data transmission to said terminal and/or datatransmission from said terminal are not detected; a step to recovercounting the time of data transmission if data transmission to saidterminal or data transmission from said terminal is detected; and a stepfor stopping counting data transmission time based on a calldisconnection request transmitted from said terminal and a step totransmit billing information including transmission time thus counted tosaid billing server.
 5. The billing information collection methodaccording to claim 4 that comprises a step for counting the time duringwhich said information processing equipment does not detect datatransmission to said terminal or data transmission from said terminaland a step for stopping counting of transmission time and transmittingto said terminal a data communication close request instructing thatcommunication of data to said terminal be closed, if time countedexceeds a specified amount.